home *** CD-ROM | disk | FTP | other *** search
- Path: qiclab.scn.rain.com!krypton!shadow
- From: shadow@krypton.rain.com (Leonard Erickson)
- Newsgroups: alt.computer.consultants,comp.edu,comp.lang.basic.misc,comp.lang.c++,comp.lang.m
- Subject: Re: Can we do programming without seeing the end user?
- Message-ID: <iioFLD7w165w@krypton.rain.com>
- Date: Tue, 26 Mar 96 21:16:41 PST
- References: <Pine.OSF.3.91a.960326020136.11952K-100000@christa.unh.edu>
- Organization: Shadownet
-
- Ben Scott <bscott@christa.unh.edu> writes:
-
- > On 24 Mar 1996, KJumoke wrote:
- >
- > > The financial or operational effects of different user interfaces in the
- > > workplace may be quite minimal in the long term.
- >
- > Never forget, that in the end, someone has to use your software.
- > Without that, there is no point what-so-ever in writing it. If the
- > software is not good for the user, it is not good software. Don't
- > discount the individual. Yes, the feelings of a single person look small
- > on paper. But, (1) that is no reason to discount the feelings of the
- > person, and (2) 2000 times small is big. If you add up the cumulative
- > effect of a poor interface, you will often find a net loss.
-
- One unfortunate tendency I've run into is a supervisor or manager, who
- will *never* be using the interface trying to dictate it. In one case,
- I'd presented several alternatives to the people who were actually
- *using* the software I was revising. They liked a menu setup that was
- noticably different from the "old way" (among other things, it grouped
- things *logically* :-)
-
- Their manager almost got physical with me about the change. <sigh>
-
- Leonard Erickson (aka Shadow)
- shadow@krypton.rain.com <--preferred
- leonard@qiclab.scn.rain.com <--last resort
-